RE: [L2CP] TLV number clash in new wadhwa draft
"Sanjay Wadhwa" <swadhwa@juniper.net> Tue, 23 May 2006 14:25 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiXom-0006HO-ID; Tue, 23 May 2006 10:25:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FiXol-0006HJ-KZ for l2cp@ietf.org; Tue, 23 May 2006 10:25:03 -0400
Received: from kremlin.juniper.net ([207.17.137.120]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiXok-0001Mh-AM for l2cp@ietf.org; Tue, 23 May 2006 10:25:03 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by kremlin.juniper.net with ESMTP; 23 May 2006 07:25:01 -0700
X-IronPort-AV: i="4.05,161,1146466800"; d="scan'208"; a="548672049:sNHT30404688"
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="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L2CP] TLV number clash in new wadhwa draft
Date: Tue, 23 May 2006 10:25:00 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2803B756CB@proton.jnpr.net>
In-Reply-To: <20060523040748.2408215C444@prattle.redback.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [L2CP] TLV number clash in new wadhwa draft
Thread-Index: AcZ97co3ek+BrcK0R7e1TxXx0Vh9UwAL/nmAABWivhA=
From: Sanjay Wadhwa <swadhwa@juniper.net>
To: parberg@redback.com, Jakob Heitz <jheitz@redback.com>, l2cp@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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
Peter Most of this doesn't belong to the list. Let us limit the discussion here to technical issues if any with the current version of the draft. Thanks -Sanjay >-----Original Message----- >From: Peter Arberg [mailto:parberg@redback.com] >Sent: Tuesday, May 23, 2006 12:08 AM >To: 'Jakob Heitz'; l2cp@ietf.org >Subject: RE: [L2CP] TLV number clash in new wadhwa draft > > >So at the moment there is no need to even read the new draft. > >Most of these changes is done because I have requested them >based on other customer discussions, non DT, and to make ANCP >more compliant to TR-101 from information it includes. > >But unfortunately the update is not made consistent, so there >is even number disagreement inside the draft. > >So for now, forget it is there, and stay at the .0 draft. > >This .01 version is actually a lot closer to the PDD, but since >mainly the DSLAM vendors kept arguing against the draft, and >Wadhwa was to slow to get it out, it will not make the DT trail >which was the idea back in January. > >Peter > >> -----Original Message----- >> From: Jakob Heitz [mailto:jheitz@redback.com] >> Sent: 22. maj 2006 15:20 >> To: l2cp@ietf.org >> Subject: Re: [L2CP] TLV number clash in new wadhwa draft >> >> Also, Access-Aggregation-Circuit-ID-ASCII >> for VLAN is specified thus: >> Access-Node-Identifier eth slot/port [:inner-vlan-id][:outer-vlan-id] >> >> Could we swap the outer and inner, like this ? >> Access-Node-Identifier eth slot/port [:outer-vlan-id][:inner-vlan-id] >> >> Jakob Heitz wrote: >> > 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 >> >> -- >> Jakob Heitz. x5475. 510-566-2901 >> >> _______________________________________________ >> 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 > _______________________________________________ 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