[L2CP] TLV number clash in new wadhwa draft
Jakob Heitz <jheitz@redback.com> Mon, 22 May 2006 22:06 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiIXY-0007O3-Ge; Mon, 22 May 2006 18:06:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiIXX-0007Ny-TV for l2cp@ietf.org; Mon, 22 May 2006 18:06:15 -0400
Received: from prattle.redback.com ([155.53.12.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiIXU-0000ce-Ki for l2cp@ietf.org; Mon, 22 May 2006 18:06:15 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 1DC9D4EF34 for <l2cp@ietf.org>; Mon, 22 May 2006 15:06:12 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09665-10 for <l2cp@ietf.org>; Mon, 22 May 2006 15:06:12 -0700 (PDT)
Received: from [127.0.0.1] (login005.redback.com [155.53.12.64]) by prattle.redback.com (Postfix) with ESMTP id 018BF4EF33 for <l2cp@ietf.org>; Mon, 22 May 2006 15:06:11 -0700 (PDT)
Message-ID: <44723600.4040507@redback.com>
Date: Mon, 22 May 2006 15:06:56 -0700
From: Jakob Heitz <jheitz@redback.com>
Organization: Redback Networks, Software Development
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2cp@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at redback.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [L2CP] TLV number clash in new wadhwa draft
X-BeenThere: l2cp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 2 Control Protocol Discussion List <l2cp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l2cp>
List-Post: <mailto:l2cp@ietf.org>
List-Help: <mailto:l2cp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=subscribe>
Errors-To: l2cp-bounces@ietf.org
For PORT UP TLVs, new addition,
2. Type (Access-Loop-Remote-Id = 0x02)
required a renumbering of
3. Type (Access-Aggregation-Circuit-ID-Binary = 0x04)
from 0x02 to 0x04.
However,
5. Type (DSL Line Attributes = 0x04):
is 0x04. A clash!
Because this one contains its own TLVs, is it even needed?
The encapsulated TLVs have no numbering clashes.
The new version is incompatible with the old due to
the renumbered items. Therefore could we please
bump the version, say to 0x32.
_______________________________________________
L2cp mailing list
L2cp@ietf.org
https://www1.ietf.org/mailman/listinfo/l2cp
- [L2CP] TLV number clash in new wadhwa draft Jakob Heitz
- Re: [L2CP] TLV number clash in new wadhwa draft Jakob Heitz
- RE: [L2CP] TLV number clash in new wadhwa draft Peter Arberg
- RE: [L2CP] TLV number clash in new wadhwa draft Sanjay Wadhwa
- RE: [L2CP] TLV number clash in new wadhwa draft Sanjay Wadhwa
- RE: [L2CP] TLV number clash in new wadhwa draft Peter Arberg