[Manet-dt] msg-semantics & msg-header-info = originator-address, ttl, hop-count, and msg-seq-number
Ian Chakeres <ian.chakeres@gmail.com> Sun, 22 January 2006 22:43 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1F0nve-0008Gt-ED; Sun, 22 Jan 2006 17:43:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1F0nvc-0008Ge-T3
for manet-dt@megatron.ietf.org; Sun, 22 Jan 2006 17:43:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23708
for <manet-dt@ietf.org>; Sun, 22 Jan 2006 17:41:51 -0500 (EST)
Received: from xproxy.gmail.com ([66.249.82.207])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0o4q-0006hC-12
for manet-dt@ietf.org; Sun, 22 Jan 2006 17:52:53 -0500
Received: by xproxy.gmail.com with SMTP id t12so586705wxc
for <manet-dt@ietf.org>; Sun, 22 Jan 2006 14:43:18 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer;
b=TJLwSbT8cXH0e9lzwSpDUGMH33JST5XINE2di0g/YgE9LX/sxUBMCCvVVD9KZ30hGZnEhshoIoxpjSNWdzq+Ex10h9KrYSxbFnUHVih2vxblvpu/TzA4Ele7AgsUyjAA8M8vmwC23Ud2y7Ai5yHLX0EqRAahzTWbjE7xoE/yfz8=
Received: by 10.70.23.1 with SMTP id 1mr5360229wxw;
Sun, 22 Jan 2006 14:43:18 -0800 (PST)
Received: from ?192.168.1.100? ( [66.235.34.131])
by mx.gmail.com with ESMTP id i17sm6500514wxd.2006.01.22.14.43.17;
Sun, 22 Jan 2006 14:43:17 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Transfer-Encoding: 7bit
Message-Id: <B6718251-66B9-4419-A9AE-49C36B6793CA@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: manet-dt@ietf.org, Thomas Heide Clausen <T.Clausen@computer.org>,
Justin Dean <jdean@itd.nrl.navy.mil>
From: Ian Chakeres <ian.chakeres@gmail.com>
Date: Sun, 22 Jan 2006 14:43:11 -0800
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc:
Subject: [Manet-dt] msg-semantics & msg-header-info = originator-address, ttl,
hop-count, and msg-seq-number
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>,
<mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>,
<mailto:manet-dt-request@ietf.org?subject=subscribe>
Sender: manet-dt-bounces@ietf.org
Errors-To: manet-dt-bounces@ietf.org
I'd like to start up the discussion on msg-semantics and msg-header- info again. How do people feel about using more bits in msg-semantics to identify the information contained in the msg-header-info? For example, if we use 4 bits in the msg-semantics we can specify which of the four fields in msg-header-info (originator-address, ttl, hop-count, and msg-seq-number) are contained in the msg. For DYMO I think that TTL is a necessity. In DYMO, originator- address, hop-count and msg-seq-number (in the msg-header-info) may or may not be used. It is still up for discussion. Instead of creating a msg-tlv TTL I would rather use the msg-header- info field and have all nodes implementing the common packet format understand how to process the generic header. Ian _______________________________________________ Manet-dt mailing list Manet-dt@ietf.org https://www1.ietf.org/mailman/listinfo/manet-dt
- [Manet-dt] msg-semantics & msg-header-info = orig… Ian Chakeres