[Megaco] TPKT header

"Atanum" <atanum@netbrahma.com> Wed, 25 July 2001 06:51 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02394 for <megaco-archive@odin.ietf.org>; Wed, 25 Jul 2001 02:51:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21838; Wed, 25 Jul 2001 01:50:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21809 for <megaco@ns.ietf.org>; Wed, 25 Jul 2001 01:50:32 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA21025 for <megaco@ietf.org>; Wed, 25 Jul 2001 01:49:35 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id BAA02332 for <megaco@ietf.org>; Wed, 25 Jul 2001 01:50:00 -0400 (EDT)
Received: (from majordom@localhost) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) id BAA13865 for megaco-list; Wed, 25 Jul 2001 01:50:04 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id BAA13860 for <megaco@fore.com>; Wed, 25 Jul 2001 01:50:02 -0400 (EDT)
Received: from brahma01.netbrahma.com ([164.164.70.67]) by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id BAA02328 for <megaco@fore.com>; Wed, 25 Jul 2001 01:49:55 -0400 (EDT)
Received: from ATANU ([172.16.72.98]) by brahma01.netbrahma.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PRXCHVHN; Wed, 25 Jul 2001 11:17:43 +0530
Message-ID: <00c901c114ce$cfdd2640$624810ac@netbrahma.com>
Reply-To: Atanum <atanum@netbrahma.com>
From: Atanum <atanum@netbrahma.com>
To: megaco@fore.com
Date: Wed, 25 Jul 2001 11:28:22 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C6_01C114FC.E95CC610"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Precedence: bulk
Subject: [Megaco] TPKT header
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Hi List,
The TPKT header as per the RFC1006 doesn't say anything about the 2nd octet other than reserved.there is no mention about its value.
the draft-rosen-megaco-interop-1-report-00.txt says the 2nd byte should contain the value 0. Which one to consider ...RFC1006 or this draft.
If somebody ignores the value of the 2nd byte is he wrong  or while sending a message he has to always fill the 2nd byte with 0 value ??
In that case can we consider in a  byte stream 0300 will always indicate the start of the TPKT packet and the next two byte will give out the length..
or  03 itself enough for indication of the start of a TPKT packet ???
Regards
Atanu Mondal