[hybi] hum #3: Message

Salvatore Loreto <salvatore.loreto@ericsson.com> Thu, 05 August 2010 16:38 UTC

Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 798AD3A6842 for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 09:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.946
X-Spam-Level:
X-Spam-Status: No, score=-103.946 tagged_above=-999 required=5 tests=[AWL=-1.348, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 WO8mv3RRQmgq for <hybi@core3.amsl.com>; Thu, 5 Aug 2010 09:38:58 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 3D46B3A6823 for <hybi@ietf.org>; Thu, 5 Aug 2010 09:38:58 -0700 (PDT)
X-AuditID: c1b4fb39-b7b91ae000001aef-12-4c5ae93ff8f6
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 9E.2A.06895.F39EA5C4; Thu, 5 Aug 2010 18:39:28 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Aug 2010 18:39:27 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Aug 2010 18:39:27 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 2149A24C9; Thu, 5 Aug 2010 19:39:27 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CC3524FC70; Thu, 5 Aug 2010 19:39:26 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 20D2C4FC48; Thu, 5 Aug 2010 19:39:26 +0300 (EEST)
Message-ID: <4C5AE93D.4040803@ericsson.com>
Date: Thu, 05 Aug 2010 18:39:25 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary="------------040209010404050403070802"
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 05 Aug 2010 16:39:27.0399 (UTC) FILETIME=[C502EB70:01CB34BC]
X-Brightmail-Tracker: AAAAAA==
Cc: SM <sm+ietf@elandsys.com>
Subject: [hybi] hum #3: Message
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2010 16:38:59 -0000

based on slide #8 in http://www.ietf.org/proceedings/78/slides/hybi-1.pdf

as Chairs we asked for a hum on the following statements:

    *   "Message" is a protocol unit with an end
    * A message may be composed of one or more "frame"s
    * Each frame has a length indication, encoded in a fixed number of
      bits (where that lengths is fixed in the specification to be written)

There was consensus of the room for the above statements.



The we have also asked  an hum on whether:

    * a message should be made of one or more frames?
    * each message should be composed on precisely one frame

The sense of the room was for the first question: a message should be 
made of one or more frames.



finally as Chairs asked for a hum on the following statements:

    * Should the message has a length?
    * Each frame has a length indication encoded in a fixed number of
      bits (where the length is fixed in the specification to be written).

and it was the room consensus on the fact that that Each frame has a 
length indication.


So unless people will raise good technical reasons against (during the 
next week):
we will declare consensus on them.


Joe Hildebrand and Salvatore Loreto
as chairs