IETF Logo Mail Archive

RE: [L2CP] TLV number clash in new wadhwa draft

"Sanjay Wadhwa" <swadhwa@juniper.net> Tue, 23 May 2006 14:14 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiXeC-0000AH-14; Tue, 23 May 2006 10:14:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiXeB-0000AC-5M for l2cp@ietf.org; Tue, 23 May 2006 10:14:07 -0400
Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiXe9-0000yJ-Sh for l2cp@ietf.org; Tue, 23 May 2006 10:14:07 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by borg.juniper.net with ESMTP; 23 May 2006 07:14:06 -0700
X-IronPort-AV: i="4.05,161,1146466800"; d="scan'208"; a="552910794:sNHT28737820"
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L2CP] TLV number clash in new wadhwa draft
Date: Tue, 23 May 2006 10:14:04 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2803B756CA@proton.jnpr.net>
In-Reply-To: <44723600.4040507@redback.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [L2CP] TLV number clash in new wadhwa draft
Thread-Index: AcZ97AgJimaFJwnqQ72rsBK3qs1QlwAhwjrQ
From: Sanjay Wadhwa <swadhwa@juniper.net>
To: Jakob Heitz <jheitz@redback.com>, l2cp@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc:
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

Known issues (thanks to Thomas and Norbert) and will be fixed. Today Access-Aggregation-Circuit-ID-Binary is not supported by any implementation.

>-----Original Message-----
>From: Jakob Heitz [mailto:jheitz@redback.com]
>Sent: Monday, May 22, 2006 6:07 PM
>To: l2cp@ietf.org
>Subject: [L2CP] TLV number clash in new wadhwa draft
>
>
>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 mailing list
L2cp@ietf.org
https://www1.ietf.org/mailman/listinfo/l2cp

v2.23.0 | Report a Bug | By Email