IETF Logo Mail Archive

RE: [Megaco] What exactly constitutes Version 1 ?

"Rosen, Brian" <Brian.Rosen@marconi.com> Fri, 05 October 2001 18:50 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 ESMTP id OAA28600 for <megaco-archive@odin.ietf.org>; Fri, 5 Oct 2001 14:50:54 -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 OAA19091; Fri, 5 Oct 2001 14:31:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19064 for <megaco@optimus.ietf.org>; Fri, 5 Oct 2001 14:31:26 -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 ESMTP id OAA28212 for <megaco@ietf.org>; Fri, 5 Oct 2001 14:31:24 -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 OAA13997; Fri, 5 Oct 2001 14:30:53 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA21326; Fri, 5 Oct 2001 14:30:52 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21) id <TLVXBB3N>; Fri, 5 Oct 2001 14:30:51 -0400
Message-ID: <313680C9A886D511A06000204840E1CF57C312@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: 'Paul Long' <plong@ipdialog.com>, megaco@ietf.org
Subject: RE: [Megaco] What exactly constitutes Version 1 ?
Date: Fri, 05 Oct 2001 14:30:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C14DCB.DA317A20"
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

In the interops, there has always been two points of confusion on TPKT.
One was "RFC1006 is a lengthy spec, what do I actually have to do?"
The answer is slap a 4 byte header in front of the message.
 
The other question is what happens to byte, aaah, 3 I think.  The answer
is, set it to zero on transmit, ignore on reception.
 
Brian

-----Original Message-----
From: Paul Long [mailto:plong@ipdialog.com]
Sent: Friday, October 05, 2001 2:10 PM
To: megaco@ietf.org
Subject: RE: [Megaco] What exactly constitutes Version 1 ?


Padma,
 
I'm confused. What do you mean by "4 byte TPKT header ... instead of
RFC1006." Section 6 in RFC1006 has always defined a 4-byte header for TPKT.
 
Paul Long
ipDialog, Inc.
 

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Padmaja Musti
Sent: Thursday, October 04, 2001 8:50 AM
To: 'Tom-PT Taylor'; Padmaja Musti; 'Harry Suede'; megaco@ietf.org
Subject: RE: [Megaco] What exactly constitutes Version 1 ?


Hi,
I think in the previous Interops there was confusion on the implementation
of TPKT /RFC1006
and there was suggestion that 4 byte TPKT header should be used instead of
RFC1006.
But this is not mentioned in the IG Jun 2001. Was it omitted inadvertently.
For the coming Interop should every one come with 4 byte TPKT header or
RFC1006 implementation.
regards,
Padma

v2.23.0 | Report a Bug | By Email