Re: [manet-dlep-rg] Slight issue with Data items

"Taylor, Rick" <> Mon, 10 March 2014 17:25 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 025341A06B2 for <>; Mon, 10 Mar 2014 10:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Rz0sO8bS9c35 for <>; Mon, 10 Mar 2014 10:25:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F419D1A064D for <>; Mon, 10 Mar 2014 10:25:24 -0700 (PDT)
Received: from unknown (HELO fr-gate2.mailhub.intra.corp) ([]) by with ESMTP; 10 Mar 2014 18:25:18 +0100
Received: from ([]) by fr-gate2.mailhub.intra.corp with Microsoft SMTPSVC(5.0.2195.7381); Mon, 10 Mar 2014 18:25:17 +0100
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 Mar 2014 18:25:17 +0100
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 Mar 2014 18:25:17 +0100
Received: from SUCNPTEXM01.COM.AD.UK.DS.CORP ([fe80::2543:10a0:fd02:b894]) by ([::1]) with mapi id 14.02.0318.004; Mon, 10 Mar 2014 17:25:16 +0000
From: "Taylor, Rick" <>
To: "Stan Ratliff (sratliff)" <>, Rick Taylor <>
Thread-Topic: [manet-dlep-rg] Slight issue with Data items
Thread-Index: AQHPPH91PCp7d2LHg0SwkWmlhgboNJra3nSA//+uEzA=
Date: Mon, 10 Mar 2014 17:25:16 +0000
Message-ID: <>
References: <> <d5a2b437-1a21-4569-9b97-5048512604bc@SUCNPTEXC01.COM.AD.UK.DS.CORP>
In-Reply-To: <d5a2b437-1a21-4569-9b97-5048512604bc@SUCNPTEXC01.COM.AD.UK.DS.CORP>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 10 Mar 2014 17:25:17.0313 (UTC) FILETIME=[B4783F10:01CF3C85]
X-TM-AS-Product-Ver: SMEX-
X-TM-AS-Result: No--17.641500-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: " Group, \(\)" <>
Subject: Re: [manet-dlep-rg] Slight issue with Data items
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DLEP Radio Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 10 Mar 2014 17:25:29 -0000

> I'll offer up a slight modification of the "London Rule" :  Experimental Data
> Items (and Vendor-specific TLVs) that are not supported by an
> implementation should be parsed (e.g. "stepped over') and silently dropped.
> Data Item TLVs that are not *understood* (e.g. TLV number not registered,
> or "reserved"), OR are out-of-context (like a Version TLV in a destination
> update message) should cause PEER_TERMINATION and closure of TCP
> session.

That will rely on a clear list of every suitable data item TLV used with each signal, which might turn into an O(N^2) documentation nightmare.

I was wondering about adding an 8bit context field to the TLV header: 8bit Type, 8bit Context, 16bit Length (seems to align nicely).

Context: 1 = Discovery Data Item, 2 = Session Initiation/Termination Data Item, 3 = Peer Data Item, 4 = Link Data Item, plus the classic experimental and reserved spaces.

This might be easier to specify, and reduces the London Rule to "Any data item received with a context field that does not match the context of the enclosing signal MUST result in PEER_TERMINATION", then all that is needed is to define the context of each signal, back to O(N) for those of you familiar with big-O notation.

I know this seems like adding error checking to the protocol, but with Vendor Extensions and experimental TLVs a bit of error checking is no bad thing, just think of it as an FEC code...

Alternatively you could consider Type and Context as one little endian 16bit value... or swap them around to make CTLV...


The information contained within this e-mail and any files attached to this e-mail is private and in addition may include commercially sensitive information. The contents of this e-mail are for the intended recipient only and therefore if you wish to disclose the information contained within this e-mail or attached files, please contact the sender prior to any such disclosure. If you are not the intended recipient, any disclosure, copying or distribution is prohibited. Please also contact the sender and inform them of the error and delete the e-mail, including any attached files from your system. Cassidian Limited, part of the Airbus Defence and Space division. Registered Office: Quadrant House, Celtic Springs, Coedkernew, Newport , NP10 8FZ. Registered in England and Wales under company number 04191036